Personal computer diagnostic test before executing operating system

ABSTRACT

A personal computer component diagnostic method is executed to recognize the status or potential problems of a computer before executing an operating system. The personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program; and executing a component functional test after executing a predetermined step. The component functional test includes a CPU MSR/MTRR test, a hard disk S.M.A.R.T. test, a boot path test and a PCI device scanning test.

CROSS-REFERENCE

This application is a continuation of application Ser. No. 11/773,809, filed Jul. 5, 2007, which claims priority to Taiwan Application Serial Number 95124697, filed Jul. 6, 2006. The entire disclosures of all the above applications are hereby incorporated by reference herein.

BACKGROUND

1. Field of Invention

The present invention relates to a personal computer component diagnostic module and test thereof. More particularly, the present invention relates to personal computer component diagnostic test before executing an operating system.

2. Description of Related Art

Without a software operating system, i.e. Windows operating system, users cannot recognize a status or potential problems of a conventional personal computer. Conventional BIOS is equipped with component basic diagnostic program, i.e. detecting whether hardware exists or not. After the BIOS component basic diagnostic program is executed, the software operating system can be loaded and operated.

In case a BIOS component basic diagnostic program is executed and the software operating system cannot be loaded, an engineer uses “trial and error” methods to fix a personal computer in addition to using low level equipment. However, it is necessary to have extra components to execute a “trial and error” method. Without extra components, a “trial and error” method is of no use. Moreover, users often seek help from the PC system suppliers even if the actual problem occurs in some component.

For the forgoing reasons, there is a need for a PC component diagnostic method before executing an operating system.

SUMMARY

It is therefore an objective of the present invention to provide a PC component diagnostic method to recognize the status or potential problems of a computer without an operating system being loaded.

In accordance with the foregoing and other objectives of the present invention, a personal computer component diagnostic method is executed before executing an operating system. The personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program; and executing a component functional test after executing a predetermined step. The component functional test includes a CPU MSR/MTRR test, a hard disk S.M.A.R.T. test, a boot path test and a PCI device scanning test.

Therefore, this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.

It is to be understood that both the foregoing general description and the following detailed description are by examples, and are intended to provide further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. In the drawings,

FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention;

FIGS. 2, 3 and 4 respectively illustrate three different embodiments of PC component diagnostic module on the motherboard according to one preferred embodiment of this invention;

FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention; and

FIG. 6 is a flowchart of personal computer component functional test according to one preferred embodiment of this invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.

FIG. 1 is a flowchart of personal computer component diagnostic test according to one preferred embodiment of this invention. In step 201, a BIOS program is called. In step 203, a component basic diagnostic program, i.e. detecting the hard disk configuration, is executed. In particular, when detecting the hard disk configuration is executed, a command (referred to as a basic command) is sent to a hard disk controller, and a response is sent back from the hard disk controller to provide information on the hard disk type or whether this hard disk supports S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) or not, etc. In step 205, a component function test is executed after executing a predetermined step and before an operating system is executed. The predetermined step can be any step after step 203 and before the component functional test is executed. In this embodiment, the predetermined step initializes a display device such that the component functional test result can be displayed on the display device. The component functional test can further detect potential errors that the component basic diagnostic program (step 203 cannot detect). For example, the hard disk can merely be recognized as a hard disk with S.M.A.R.T. functionality in step 203, but further tests, i.e., a rotation speed test, can be executed in step 205.

FIGS. 2, 3 and 4 respectively illustrate three different embodiments of the PC component diagnostic module on the motherboard according to one preferred embodiment of this invention. The component functional test (step 205) is executed by a component functional test module, which is installed as an optional ROM on the motherboard 100. FIG. 2 illustrates the component functional test module 110, which is saved in an independent optional ROM 108 on the motherboard 100 and separate from the BIOS component basic diagnostic module 106. FIG. 3 illustrates the component functional test module 110, which is saved in a PCI optional ROM 108 b (on a PCI card 107) and separate from the BIOS component basic diagnostic module 106. FIG. 4 illustrates the component functional test module 110, which is saved in BIOS optional ROM 108 a and integrated with the BIOS component basic diagnostic module 106. No matter what embodiment is used, the component functional test module 110 can achieve the same result.

FIG. 5 illustrates a complete PC component diagnostic module according to one preferred embodiment of this invention. FIG. 6 is a flowchart of a personal computer component functional test according to one preferred embodiment of this invention.

In step 202, when the CPU 102 (illustrated in FIGS. 2, 3 and 4) calls the component functional test program, the component functional test program is duplicated in a random access memory 104 and decompressed. In order to preserve enough buffer memory to execute the component functional test, enough space (at least 512K) in the random access memory 104 should be confirmed first.

In step 204, a personal computer configuration is detected first so as to prepare the following steps of the component functional test program. This step is executed by a detection module 112 in FIG. 5.

In step 206, a scan module 118 of FIG. 5 executes a PCI device scanning test.

In step 208, a CPU diagnostic module 120 of FIG. 5 executes a CPU MSR (Module Specific Register)/MTRR (Memory Type Range Register) test.

In step 210, a hard disk diagnostic module 114 of FIG. 5 executes a S.M.A.R.T. (Self-Monitoring, Analysis, and Reporting Technology) test.

In step 212, a path module 116 of FIG. 5 executes a boot path test, i.e. a network boot component test.

Steps 206-212 can be executed without specific sequence and can be deducted according to demands. The component functional test can be launched by pressing a specific key, i.e. a button or switch connected with the PC system, selected in the BIOS, by a decision made by the component basic diagnostic program. After the component functional test is completed, the test result can be outputted by a display device, a log file containing error codes or a speaker. Users are able to recognize the computer status and potential problems as a reference source to fix the computer.

According to preferred embodiments of the present invention, this component diagnostic method can assist users or agents to recognize the computer status or potential problems without a Windows operating system such that a motherboard, a back bone system or a notebook PC need not be sent back to its supplier more often than not.

It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the present invention without departing from the scope or spirit of the invention. In view of the foregoing, it is intended that the present invention cover modifications and variations of this invention provided they fall within the scope of the following claims and their equivalents. 

1. A personal computer component diagnostic method before an operating system is executed, the personal computer component diagnostic method comprising: calling a BIOS program; executing a component basic diagnostic program for detecting the personal computer; when receiving a trigger event, selecting and executing at least one specific component functional test for detecting a configuration of the specific computer component; and displaying the configuration of the specific computer component.
 2. The personal computer component diagnostic method of claim 1, the functional test can be terminated by a interrupt signal.
 3. The personal computer component diagnostic method of claim 1, when the bios receiving a trigger event, the component functional test for recognize the computer component status and potential problems.
 4. The personal computer component diagnostic method of claim 1, when bios receiving a trigger event, duplicating and executing at least one specific component functional test for specific of the computer component in a memory.
 5. A personal computer component diagnostic module for executing a diagnostic method before an operating system is executed, the personal computer component module comprising: a random access memory; a BIOS module; a CPU for calling and executing the BIOS module in the random access memory; and a component functional test module for executing a component functional test program; when bios receiving a trigger event, duplicating and executing at least one specific component functional test program for detecting a configuration of the specific computer component in a memory.
 6. The personal computer component diagnostic module of claim 5, component functional test program for detecting configuration of a hard disk, or configuration of a boot path or configuration of a PCI device, or configuration of a CPU MSR/MTRR.
 7. The personal computer component diagnostic module of claim 5, the component functional test module is installed as an optional ROM on the motherboard.
 8. The personal computer component diagnostic module of claim 5, the component functional test module is saved in an independent optional ROM.
 9. The personal computer component diagnostic module of claim 5, the component functional test module is saved in a PCI optional ROM.
 10. The personal computer component diagnostic module of claim 5, when the bios receiving a trigger event, the component functional test for recognize the computer component status and potential problems. 